home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 8
/
QRZ Ham Radio Callsign Database - Volume 8.iso
/
pc
/
files
/
f6fbb
/
carbon_3.exe
/
CARBON3.DOC
< prev
next >
Wrap
Text File
|
1992-12-28
|
16KB
|
327 lines
CARBON SERVER PROGRAM (VERSION 3)
=================================
FOR F6FBB BBS
=============
WRITTEN BY KEN WOOD G3WCS
=========================
IMPORTANT
=========
This software is released into the Public Domain and is designed for
use by radio amateurs running BBS systems. It may not be sold under
any circumstances. It may be passed freely from one person to
another, provided there is no charge, either financial or otherwise.
The only condition regarding the passing on of this software is that
the original documentation is included. I make this stipulation
because problems arising with previous releases have inevitably been
due to people attempting to run the software without the correct
documentation. To this end, you must distribute the archived file as
supplied originally.
OVERVIEW
========
This server has the ability to duplicate any number of identical
messages after reception of one uniquely addressed message to a
certain server callsign. According to the way that the distribution
file is set up, the SYSOP has the option to allow only specified
callsigns, or alternatively any callsign, to send messages to the
server for duplication. In addition, the carboned message may
optionally include a list of the callsigns to whom the message has
been dispatched. This version was written taking into account the
wishes of various users. I hope that the server is sufficiently
flexible to cater for all needs.
Here is a summary of the features included in this version.
1. The server runs immediately on reception of the incoming message.
I have included this facility to increase expedition and because the
configuration options are comprehensive enough to prevent most abuse.
2. The acknowledgement message sent to the sender of the incoming
message is now more accurately addressed.
3. The outgoing messages show the "from" callsign as that of the BBS
at which the server operation took place, not the user, as before.
This is to prevent incorrect White Page operation which will otherwise
attribute an incorrect home BBS to a user whose CARBON message has
been daisy chained from one CARBON server to another. The senders
callsign is embedded in the actual message and will be correctly read
by any subsequent CARBON process.
4. A wildcard entry is allowed in the distribution file, meaning
that any station may send a message to the server. Previously,
stations inputting messages had to be on an authorised list. The list
facility is still retained and the SYSOP may decide which to use. If
several server callsigns are in use at the BBS, each server callsign
now has the option of wildcard entry or authorised list. You may mix
at will.
5. Each carboned message may or may not include a list of the
stations who will receive the message. Once again the SYSOP has the
option to enable or disable this facility on any of the server
callsigns he has installed.
6. There is now no limit to the minimum size of message sent to the
server. Previously, messages had to contain at least two lines of
text to be correctly duplicated.
7. There is no limit to the number of callsigns on a distribution
list. Thus for large distributions there is no need to have one
server message calling another at the same BBS.
8. Hierarchical addresses are now permitted in the server
distribution list.
9. When an incoming message is received from another CARBON3 server,
the server name and distribution list information are not duplicated.
This reduces the message size and removes redundant information.
10. In the event that the server is unable to find one of the
required disk files, a message will be generated for the SysOp
advising the problem.
OPERATION
=========
Upon receipt of a correctly addressed input message, the F6FBB BBS
software automatically exports it to a temporary disk file.
Immediately after this the CARBON server is executed. The temporary
message is read, as is the distribution file called CARBON.DIS.
Depending upon the configuration of CARBON.DIS, the message is
duplicated to several callsigns. In addition, a message for the BBS
SYSOP is generated informing him of the server activity. A further
message for the originator of the message is created advising him of
successful distribution. He is not sent a copy of the duplicated
message. In the event that an unauthorised attempt is made to use the
server, the SYSOP will receive an informative message. The sender of
the unauthorised message will not receive an acknowledgement. After
completion of these procedures the temporary disk file is
automatically deleted.
COMPATIBILITY WITH PREVIOUS VERSIONS
====================================
This version is a complete rewrite of the source code. Messages which
have been processed by an earlier version and sent to CARBON3 for
daisy chaining will still work. However, the previous server
information and any distribution list will not be removed. For this
reason it is advisable for your neighbours to upgrade to this new
version as well.
SETTING UP
==========
Please pay careful attention to the following set up procedure. Most
problems occur because a mistake or omission has been made in one or
other of the files. Please check all these before reporting a
problem.
When modifying or creating files remember to use an ASCII text editor.
A word processor, such as Wordstar [tm] (in document mode), which may
embed hidden control codes is NOT suitable.
REMOVAL OF OLD CARBON SERVER (VERSION ONE)
------------------------------------------
This section only applies if you are presently using my original
CARBON1 server. If you are not, please skip forward to the next
section.
1. Delete the existing CARBON.EXE from the FBB or BIN directory.
2. Delete the following line (or your equivalent) from CRON.SYS, in
the FICHIERS or SYSTEM directory :-
0-23 C:\FBB\CARBON.EXE C:\FBB\ or X C:\FBB\CARBON.EXE C:\FBB\.
Leave the lines relating to any other servers intact.
3. In the file BBS.SYS in the FICHIERS or SYSTEM directory, remove
the line which mentions the CARBON servers. This will look something
like :-
61 CARBON
Remember to leave the "61" present, just delete the CARBON letters.
Be sure not to delete the lines relating to other BBS or export
entries.
4. In the file FORWARD.SYS delete the lines relating to the CARBON
server forwarding. These will look something like :-
A CARBON
P @
C C:\FBB\CARBON.OUT
B CARBON
F CC1LOC
F CC1CLU
------
Be sure to leave the lines relating to the other servers intact.
5. Modify the file CARBON.DIS to comply with the syntax in the next
section on INSTALLATION.
REMOVAL OF OLD CARBON SERVER (VERSION TWO)
------------------------------------------
The upgrade from CARBON2 to CARBON3 is simply a matter of replacing
the program file CARBON.EXE with the new version. Please note the
previous remarks about receiving carboned messages from earlier
versions for subsequent daisy chaining.
INSTALLATION
------------
1. Copy the program CARBON.EXE from the distribution disk (after
unarchiving) to your FBB or BIN directory.
2. Edit the file INIT.SRV in the FBB directory. At the end of the
file are several lines specifying which servers you have installed.
You must make a separate entry for each server callsign you wish to
use. For example, assume that you will run three server addresses:-
CC1COM for all committee members, FBB99 for distribution of messages
about F6FBB software and CC1CLU for messages to local club members.
The lines in INIT.SRV would be something like :-
#
#
--------
# List of the services. There is no limit to the number of
# services. The list should end with a series of dashes.
#
CC1COM CARBON.EXE Committee Members Server
FBB99 CARBON.EXE FBB News Distribution Server
CC1CLU CARBON.EXE Local Radio Club Members News
#
--------
#
# End of initialisation file.
#
Obviously the plain language description for each callsign is up to
you and will be shown to users when they use the PS command on the
BBS.
3. Create (or modify) a file called CARBON.DIS which MUST exist in
the FBB directory. The best way to explain this file is to show an
example with comments. An example follows. DO NOT include the
comments, such as "<===== Server callsign" in your file, they are
for explanation only. Use only the left hand side of the listing.
[CC1COM] <===== Server Callsign.
G3WCS <===== These callsigns are
G3ZZJ <===== permitted to send input
G4OAR <===== messages to the CC1COM
G4WSD <===== server callsign.
(DISTRIBUTION)
LIST <===== Msgs will have distribution list.
G6FCI @ GB7FCI <===== These callsigns will
G3ZZJ @ GB7CHS <===== receive the carboned
G4OAR @ GB7OAR <===== message.
G4WSD @ GB7CRG
G4PGO @ GB7LIV
[FBB99] <===== Server Callsign.
*.* <===== Anybody may send message to server.
(DISTRIBUTION)
LIST <===== Msgs will have distribution list.
G6FCI @ GB7FCI <===== These callsigns will
G0NGL @ GB7NWP <===== receive the carboned
G4OAR @ GB7OAR <===== message.
G3WCS @ GB7CHS
[CC1CLU] <===== Server Callsign.
*.* <===== Anybody may send message to server.
(DISTRIBUTION)
NOLIST <===== No distribution list in messages.
G3WCS @ GB7CHS <===== These callsigns will
G3ZZJ @ GB7CHS <===== receive the carboned
G4OAR @ GB7OAR <===== message.
G4WSD @ GB7CRG
G0NGL @ GB7NWP
G8AEN @ GB7BEV
The example clearly shows the syntax for the various formats. LIST
indicates that each carboned message contains a list of all the
callsigns who have been sent the message. NOLIST indicates that
messages will not include this list. This has been incorporated to
reduce message size where a SYSOP has a large distribution list and to
reduce network congestion.
There are a couple of important points here. There must be no blank
lines in the file. Note the difference in the brackets used for the
carbon callsign designator compared with the distribution list. You
may place hierarchical routings after the "@" symbol (eg. DK2LK @
DB1JH.DEU.EU). The indentation of the bracketed text is not required
but may be used to distinguish between blocks. This is normal
programming technique.
APPENDED TEXT
=============
You may enter a message to the server from the BBS keyboard and append
text from another text file, (eg. SP FBB99 + C:\TEXT.DOC). Please
ensure that your appended text file does not contain any embedded
control codes or other non printable characters. See the previous
notes on this subject.
MEMORY REQUIREMENTS
===================
When FBB BBS is loaded and running, the status line will show how much
free memory is available. This is indicated on the right hand side
and an example might be :- Ok:122040.
The number of free bytes is governed by various factors, such as
whether you are running EMS or XMS, and what items you have loaded
into high memory. When any server, be it CARBON or another program,
is executed some of that free memory is used. After completion of the
server operation the memory is returned to the system for other use.
It is advisable to arrange your system configuration to leave at least
100 Kbytes showing free on the status line. CARBON is a compact
program and does not require a great deal of memory in which to run.
This is due to the fact that all information required is read from
disk at run time and not stored in memory. This is the reason why
there is no restriction to the number of callsigns in the distribution
list. Some servers require much more free memory, hence the advice to
leave about 100 Kbytes free. Obviously, with an extremely small
amount of free memory, even CARBON will not function correctly.
ERROR REPORTS
=============
If the server is unable to find one of the required disk files, it
will in most cases, generate a message to the BBS SysOp advising why
the operation has failed. This report will be appended to MAIL.IN and
appear as a normal system message.
FINALLY
=======
A user document is included with the distribution. The SYSOP may
place this in the "files" area so that users may see the input message
syntax, without reading the full SYSOP instructions.
The server has been extensively tested but the old adage, "There is
always one more bug", must prevail.
Please report any problems or indeed any suggestions for improvement
to me by packet radio.
Ken Wood. G3WCS.
SYSOP GB7CHS.#11.GBR.EU
Cheshire NTS Mailbox.
28/12/92.
Ver 3.10
CARBON3.DOC